support multiple testsets in one gradle project #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have in many projects unit tests and integration tests in different test sets.
JaCoCo can handle this out of the box, but printCoverage only prints the coverage of the unit tests.
So I added a loop over the existing test sets and print each coverage.
To be backwards-compatible, the single test sets print the name of the test set so that this does not clash with the existing grep for "Coverage: ".
The resulting Coverage is just the maximum value of the test sets as we are here not able to differ if the coverage is overlapping or not - usually it is.